Discarding a Duplicate Packet of an RLC Entity in Response to an Acknowledgement

ABSTRACT

A wireless device receives an indication for activation of packet data convergence protocol (PDCP) packet duplication of a radio bearer associated with a first radio link control (RLC) entity and a second RLC entity. A packet of the radio bearer is duplicated. The packet to the first RLC entity is provided. A duplicate packet to the second RLC is provided. The packet of the first RLC entity is transmitted. An acknowledgement of a successful delivery for the packet of the first RLC entity is received. In response to the acknowledgement, the duplicate packet of the second RLC entity is discarded.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/933,807, filed Mar. 23, 2018, which claims the benefit of U.S.Provisional Application No. 62/475,600, filed Mar. 23, 2017, which ishereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example frame structure as per anaspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 10A, and FIG. 10B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 11 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 12 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 13 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 14 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 15 is a diagram of an example mapping of logical channels totransmission durations as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is a diagram of an example packet duplication procedure as peran aspect of an embodiment of the present disclosure.

FIG. 17 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of packetduplication. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control CHannel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic CHannel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel IDentifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank Indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 124A, 124B), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface. In this disclosure,wireless device 110A and 110B are structurally similar to wirelessdevice 110. Base stations 120A and/or 120B may be structurally similarlyto base station 120. Base station 120 may comprise at least one of a gNB(e.g. 122A and/or 122B), ng-eNB (e.g. 124A and/or 124B), and or thelike.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, and dual connectivity or tight interworkingbetween NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 andSSB/PBCH are spatially quasi co-located and resource elements associatedwith the downlink CSI-RS 522 are the outside of PRBs configured forSSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrieras per an aspect of an embodiment of the present disclosure. Amulticarrier OFDM communication system may include one or more carriers,for example, ranging from 1 to 32 carriers, in case of carrieraggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example framestructure. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 9 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 9is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 10A and FIG. 10B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 10A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 10B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 11 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg1 1220 transmissions, one or moreMsg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RS s with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-Response Window) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 12 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 13 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. 120A or 120B) may comprise a base station central unit (CU) (e.g.gNB-CU 1420A or 1420B) and at least one base station distributed unit(DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional splitis configured. Upper protocol layers of a base station may be located ina base station CU, and lower layers of the base station may be locatedin the base station DUs. An F1 interface (e.g. CU-DU interface)connecting a base station CU and base station DUs may be an ideal ornon-ideal backhaul. F1-C may provide a control plane connection over anF1 interface, and F1-U may provide a user plane connection over the F1interface. In an example, an Xn interface may be configured between basestation CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 14 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC_Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

Transmission reliability and latency enhancement are example aspects ofultra-reliable low-latency communications (URLLC). In an example,multi-connectivity may enhance reliability for URLLC. In an example,multi-connectivity may comprise packet duplication, link selection, etc.In an example, packet duplication may be used for user-plane and/orcontrol-plane traffic. In an example, LTE-NR dual connectivity may usepacket duplication. In an example, the packet data convergence protocol(PDCP) function in a transmitter may enable packet duplication and thePDCP function in the receiver may enable duplicate packet removal. In anexample, radio link control (RLC) retransmission (e.g., ARQ) may not beused for URLLC, e.g., for meeting the user-plane latency requirements.In an example, redundancy schemes operating below PDCP and/or in carrieraggregation (CA) scenarios may be used for the reliability/latencyenhancement of URLLC.

In an example in NR, multi-connectivity (MC) may comprisedual-connectivity (DC) and/or carrier aggregation (CA). In an example,multi-connectivity may comprise collocated eNBs/gNBs and/ornon-collocated eNBs/gNBs. In an example, packet duplication may be basedon PDCP with a DC architecture. In an example, packet duplication may beused with centralized and/or non-centralized PDCP. In an example, packetduplication backhaul may be used with different latencies and/ordifferent scheduler implementations (e.g., in LTE-NR integration).

In an example, PDCP duplication may be used in NR. In an example, packetduplication may be in lowers layers, e.g., MAC. In an example, DC mayuse a plurality of (e.g., two) MAC entities. In an example, the MACentities and/or the schedulers in MAC entities may be coordinated. In anexample, in CA, a common MAC entity, e.g., a scheduler, may controltransmissions on a plurality of carriers. In an example, packetduplication may be used with CA. In an example, the MAC layer may haveinformation (e.g., timely information) on radio channel qualitymeasurements (such as channel state information (CSI) report, ACK/NACKfeedback, etc.).

In an example, TTI repetitions may be configured e.g., incoverage-limited scenarios. TTI repetitions may increase thereliability. TTI repetitions may increase latency. In an example, theTTI repetitions may be performed on one or more carriers. In an example,with TTI repetitions, the received soft bits of multiple consecutivetransmissions within a same HARQ process may be combined. Soft combininggain and/or incremental redundancy gains (e.g., if supported within TTIrepetitions) may be achieved.

In an example, duplicate transmission of MAC PDUs (e.g., same transportblocks) may be used. In an example, two or more transport blocks (TBs)of a same size may be created by MAC multiplexing and assembly entity.In an example, two or more TBs may comprise a same duplicated MAC PDU.In an example, HARQ transmissions among carriers may be coupled, e.g.,using a same transport block size (TBS). In an example, a receiver mayuse joint decoding (e.g., soft combining) of the transmissions. In anexample, HARQ feedback may be aligned among the carriers. The RLCduplicate discard function may be used to handle the duplicates.

In an example, duplicate transmission of MAC SDUs, e.g., RLC PDUs and/orRLC PDU segments may be used. In an example, MAC multiplexing andassembly entity may transmit MAC SDU duplicates via a plurality ofcarriers. In an example, the HARQ transmissions among the carriers, e.g.transport block size (and required spectrum), HARQ feedbacktransmissions, etc. may be independent. In an example, a plurality ofcarrier bandwidths (e.g., numerologies) and/or carriers with differenttraffic loads may be considered. In an example, RLC duplicate discardfunction may be used at the receiver to handle the duplicates.

In an example, NR MAC may support data duplication in carrieraggregation. In an example, the MAC may be configured to duplicate andtransmit MAC SDUs among a plurality of carries. In an example, HARQoperation of the transmissions may be independent. In an example,duplicate discard functionality of RLC may be used to discard theduplicates.

In an example, PDCP split bearer and/or PDCP split bearer architecturemay be used in CA. In an example, a plurality of RLC entities may beconfigured corresponding to a PDCP bearer. In an example, PDCP maycomprise the duplication function and/or duplicate discard function. Inan example, duplicate data may be mapped to two or more logicalchannels. In an example, MAC multiplexing entity may map data of the RLCentities to different carriers that may be independently transmitted bythe HARQ entities associated with the corresponding carriers. In anexample, logical channel carrier restrictions may be applied. In anexample, one or more flags may be configured for a logical channel toallow/forbid scheduling on one or more carriers. In an example, PDCPsplit bearer with duplication function may be used in CA architecture.In an example, duplication for CA may build on the PDCP split bearer forduplication to two or more logical channels associated with a MACentity. In an example, for duplication with CA, transmissionrestrictions may be configured for one or more carriers per logicalchannel.

In an example, NR MAC may support data duplication in carrieraggregation by transmitting data from different logical channels usingdifferent cells/carriers (e.g. by defining carrier restrictions for alogical channel). Data duplication and duplicate discard may be done inPDCP layer. The PDCP split bearer may be configured with a plurality oflogical channels associated to a same cell group/MAC. In an example,data duplicated on PDCP and provided to the different logical channelsmay be transmitted by MAC via a plurality of carriers.

In an example, using MAC duplication, a same two or more transportblocks (TB) may be transmitted across a plurality of legs, e.g., usingone or more MCS and/or redundancy versions. In an example, separate HARQfunctions may operate in each leg, e.g., in CA with a HARQ entitycomprising a plurality of HARQ processes for a carrier. In an example, aTB may be encoded/decoded and/or go through HARQ process independently.A duplication detection/removal mechanism may be used in MAC layer. Inan example, upper layers may handle the duplication detection.

In an example, packet duplication in MAC may be above the HARQ function(e.g., a function per leg) or at the HARQ function level (e.g., singlefunction for sending and combining redundancy versions). In an example,packet duplication in MAC above the HARQ function (e.g., one functionper leg) may use a duplication detection/removal function in MAC, or inhigher layers.

In an example, packet duplication may be used for user-plane and/orcontrol-plane in NR PDCP. In an example, redundancy schemes operatingbelow PDCP may be used. In an example, a duplication scheme operating atthe MAC sublayer may enable a plurality of transmissions of a transportblock over a plurality of resource sets to provide diversity gain e.g.,against fading, interference and/or link blockage (e.g., shadowing). Thedifferent resource sets may be separated in time, frequency and/or spacedomains. In an example, at the receiver, the transmissions may besoft-combined and/or processed separately.

In an example, PDCP packet duplication may be configured by radioresource configuration (RRC) signaling, e.g., per bearer and/or splitradio bearer. In an example, PDCP packet duplication may be configuredper UE using higher layer signaling (e.g., RRC). In an example, packetduplication may be enabled/disabled considering e.g., UE mobility, cellresource availability, backhaul loads and latency, etc. In an example,PDCP packet duplication may be activated or deactivated dynamicallythrough downlink control signaling (e.g., physical layer and/or MAClayer signaling). In an example, a UE may initiate duplication e.g.,based on triggering one or more criteria (e.g. measurements of L1, L2signals, or radio resource management (RRM) and/or radio link monitoring(RLM) events, etc.). In an example, a UE may autonomously activate ordeactivate PDCP packet duplication based on one or more configuredcriteria. The one or more criteria may be configured e.g., with RRC. Inan example, a UE may receive a configuration of a prohibit timer (e.g.,PDCP duplication prohibit timer). In an example, a UE may start thetimer when it receives control signaling from gNB/network indicatingthat PDCP duplication may be deactivated. The UE may autonomouslyactivate duplication when the timer is expired. The timer may be set toinfinity to disable UE autonomous activation of PDCP duplication.

In an example, with URLLC packet duplication at PDCP, a UE may reportdata in its PDCP buffer to a MAC entity in multi-connectivity. In anexample, duplicated data may be considered as new data available fortransmission. In an example, the duplicated data may be reported andtransmitted, e.g., in the same manner as other data. In an example, forMAC buffer status reporting, the UE MAC may include amount of dataresulting from the PDCP duplication function as data available fortransmission. In an example, data duplicates may use separate uplinkgrants. In an example, a grant may be unique per cell group. In anexample, assignment between a PDCP duplicate PDU and a MAC entity may bedone when the duplicate PDUs are generated in PDCP. In an example, a UEmay trigger BSR/SR to an applicable MAC entity. In an example, forresource allocation based on dynamic scheduling, a UE may assign aduplicate PDCP PDU to different MAC entities and triggers BSR/SR for anapplicable MAC entity when PDCP duplication is active.

In an example, PDCP at a transmitter may support duplicated packettransmission over a plurality of links. In an example, PDCP at areceiver may perform duplication detection/removal. In an example, for aCA scenario, where transmission points on different carrier frequenciesmay be connected by ideal backhaul, PDCP duplication may be applied,e.g., based on Dual-Connectivity/Multi-Connectivity framework. In anexample, PDCP duplication based on Dual-Connectivity/Multi-Connectivityframework may be applied to scenarios where transmission points ondifferent carrier frequencies are connected by ideal backhaul. In anexample redundancy operation below PDCP, duplication may be at RLClayer. In an example, RLC entity at a transmitter may make duplicatetransmissions of a PDU. In an example, RLC entity at a receiver side mayremove received duplications. In an example, redundancy operation at MAClayer may be MAC SDU duplication and/or autonomous HARQ redundanttransmission.

In an example, a RLC PDU may correspond to a PDCP PDU. In an example, aduplicated RLC PDU may consist of a duplicated PDCP PDU. In an example,duplicate transmission of RLC PDUs may be equivalent to duplicatetransmission of PDCP PDUs. In an example carrier aggregation (CA)scenario (e.g., ideal backhaul), PDCP entity and RLC entity may share asame topology of transmission points and backhaul structure. In anexample, MAC SDU duplication may use one HARQ entity per componentcarrier/cell. In an example, a MAC TB may be transmitted by a HARQprocess of a HARQ entity at a carrier. The duplicated MAC SDUs may be inthe respective TBs generated for different carriers. The duplication maybe at MAC SDU level, which may correspond to a RLC PDU and in turn to aPDCP PDU. In an example, a MAC SDU may not have a sequence number in NR.

In an example, different redundancy versions of a MAC TB may betransmitted over a plurality of aggregated carriers. In an example, aHARQ process may transmit different RVs of a MAC TB over a plurality ofcomponent carriers. At the receiver, soft combining may be used. In anexample, a MAC TB may consist of a plurality of MAC SDUs/RLC PDUs/PDCPPDUs. In an example, packet duplication may be applied to data radiobearers (DRBs)/logical channels carrying URLLC like services.

In an example, a gNB may configure/enable/disable data redundancy belowPDCP layer, considering radio conditions and functionalities provisionedin other layers. In an example, a logical channel may be mapped to oneor more numerologies/TTI durations. In an example, if a logical channelmay be mapped to one or more numerologies/TTI durations, duplicate dataof the logical channel may be transmitted over the one or morenumerologies (e.g., in a single carrier and/or multiple carriers).

In an example, support for packet duplication function may be configuredper radio bearer. In an example, a UE may enable/disable packetduplication function. In an example, the gNB may indicate the UE to turnon/off the duplication function (e.g., using RRC and/or physical layerand/or MAC layer signaling). In an example, for a radio bearer withpacket duplicate function, enabling/disabling packet duplicationfunction may be dynamically controlled.

In an example, for UL packet duplication using Dual connectivity inNR-NR interworking scenario, the UL PDCP entity of the radio bearer maycoordinate the transmission of the UL PDCP PDU towards the secondarycell group (SCG) and master cell group (MCG) by indicating the dataavailability of the same UL PDCP SDU in the buffer status reports (BSRs)to both MCG and SCG. In an example, the wireless device may transmitPDUs of a same PDCP SDU in the logical channels of the MCG and SCG. Inan example, the UL PDCP entity may maintain the data availability forthe MCG and the SCG separately (e.g. by maintaining separate PDCP SDUbuffers for MCG and SCG, or by maintaining separate available orunavailable indications corresponding to SDUs in the same buffer). In anexample, whether to allow for duplication and the number of duplicationsmay be configurable via RRC signaling per radio bearer.

In an example, the BSR procedure and SR triggering may be similar as innormal operation without packet duplication. The BSR and SR may beseparately triggered by the MAC entities for MCG and SCG on the UE side.In an example, the logical channel(s) corresponding to URLLC may beconfigured to have highest priority and/or higher priority than othertraffic channels. In an example, the logical channel prioritization(LCP) may prioritize the URLLC logical channel(s) when generating andsending the MAC PDU to the lower layers for the UL grant (e.g.,configured or dynamic) corresponding to the numerology configured forthe URLLC logical channel. In an example, for the DL packet duplicationat the PDCP level, the DL RX PDCP entity may discard the duplicated PDCPPDUs e.g., if duplicate reception is detected.

In an example, RRM measurement for mobility in the connected mode mayprovide information for the gNB/network to manage addition and removalof a cell in multi-connectivity configuration. In an example,semi-static (e.g., using RRC) and dynamic signaling may control whichlegs of a split bearer, data may be duplicated. In an example, RRMmeasurements may be considered as baseline input for the dataduplication control, e.g., a set of RSRP threshold.

In an example, for DL and UL, duplication for CA may use PDCPduplication to more than one logical channel. In an example, theduplicated PDCP PDUs may be sent over a plurality of (e.g., different)carriers. In an example, the logical channels with data and the logicalchannels with duplicate data may be handled by one MAC entity. In anexample, the logical channels with data and the logical channels withduplicate data may be handled by two or more MAC entities.

In an example, a wireless device may receive one or more messagescomprising one or more radio resource configuration (RRC) messages fromone or more base stations (e.g., one or more NR gNBs and/or one or moreLTE eNBs and/or one or more eLTE eNBs, etc.). In an example, the one ormore messages may comprise configuration parameters for a plurality oflogical channels. In an example, the one one or messages may comprise alogical channel identifier for each of the plurality of logicalchannels. In an example, the logical channel identifier may be one of aplurality of logical channel identifiers. In an example, the pluralityof logical channel identifiers may be pre-configured. In an example, thelogical channel identifier may be one of a plurality of consecutiveintegers.

In an example, the plurality of logical channels configured for awireless device may correspond to one or more bearers. In an example,there may be one-to-one mapping/correspondence between a bearer and alogical channel. In an example, there may be one-to-manymapping/correspondence between one or more bearers and one or morelogical channels. In an example, a bearer may be mapped to a pluralityof logical channels. In an example, data from a packet data convergenceprotocol (PDCP) entity corresponding to a bearer may be duplicated andmapped to a plurality of radio link control (RLC) entities and/orlogical channels. In an example, scheduling of the plurality of logicalchannels may be performed by a single medium access control (MAC)entity. In an example, scheduling of the plurality of logical channelsmay be performed by a two or more MAC entities. In an example, a logicalchannel may be scheduled by one of a plurality of MAC entities. In anexample, the one or more bearers may comprise one or more data radiobearers. In an example, the one or more bearers may comprise one or moresignaling radio bearers. In an example, the one or more bearers maycorrespond to one or more application and/or quality of service (QoS)requirements. In an example, one or more bearers may correspond to ultrareliable low latency communications (URLLC) applications and/or enhancedmobile broadband (eMBB) applications and/or massive machine to machinecommunications (mMTC) applications.

In an example, a first logical channel of the plurality of logicalchannels may be mapped to one or more of a plurality of transmissiontime intervals (TTIs)/transmission durations/numerologies. In anexample, a logical channel may not be mapped to one or more of theplurality of TTIs/transmission durations/numerologies. In an example, alogical channel corresponding to a URLLC bearer may be mapped to one ormore first TTIs/transmission durations and a logical corresponding to aneMBB application may be mapped to one or more second TTIs/transmissiondurations, wherein the one or more first TTIs/transmission durations mayhave shorter duration than the one or more second TTIs/transmissiondurations. In an example, the plurality of TTIs/transmissiondurations/numerologies may be pre-configured at the wireless device. Inan example, the one or more messages may comprise the configurationparameters of the plurality of TTIs/transmission durations/numerologies.In an example, a base station may transmit a grant/DCI to a wirelessdevice, wherein the grant/DCI may comprise indication of a cell and/or aTTI/transmission duration/numerology that the wireless device maytransmit data. In an example, a first field in the grant/DCI mayindicate the cell and a second field in the grant/DCI may indicate theTTI/transmission duration/numerology. In an example, a field in thegrant/DCI may indicate both the cell and the TTI/transmissionduration/numerology.

In an example, the one or more messages may comprise a logical channelgroup identifier for one or more of the plurality of the logicalchannels. In an example, one or more of the plurality of logicalchannels may be assigned a logical channel group identifier n, 0≤n≤N(e.g., N=3, or 5, or 7, or 11 or 15, etc.). In an example, the one ormore of the plurality of logical channels with the logical channel groupidentifier may be mapped to a same one or more TTIs/transmissiondurations/numerologies. In an example, the one or more of the pluralityof logical channels with the logical channel group identifier may onlybe mapped to a same one or more TTIs/transmissiondurations/numerologies. In an example, the one more of the plurality oflogical channels may correspond to a same application and/or QoSrequirements. In an example, a first one or more logical channels may beassigned logical channel identifier(s) and logical channel groupidentifier(s) and a second one or more logical channels may be assignedlogical channel identifier(s). In an example, a logical channel groupmay comprise of one logical channel.

In an example, the one or more messages may comprise one or more firstfields indicating mapping between the plurality of logical channels andthe plurality of TTIs/transmission durations/numerologies and/or cells.In an example, the one or more first fields may comprise a first valueindicating a logical channel is mapped to one or more first TTIduration/transmission duration shorter than or equal to the first value.In an example, the one or more first fields may comprise a second valueindicating a logical channel is mapped to one or more second TTIdurations/transmission durations longer than or equal to the secondvalue. In an example, the one or more first fields may comprise and/orindicate one or more TTIs/transmission durations/numerologies and/orcells that a logical channel is mapped to. In an example, the mappingmay be indicated using one or more bitmaps. In an example, if a value of1 in a bitmap associated with a logical channel may indicate that thelogical channel is mapped to a corresponding TTI/transmissionduration/numerology and/or cell. In an example, if a value of 0 in thebitmap associated with a logical channel may indicate that the logicalchannel is not mapped to a corresponding TTI/transmissionduration/numerology and/or cell. In an example, the one or more messagesmay comprise configuration parameters for the plurality of the logicalchannels. In an example, the configuration parameters for a logicalchannel may comprise an associated bitmap for the logical channelwherein the bitmap may indicate the mapping between the logical channeland the plurality of TTIs/transmission durations/numerologies and/orcells.

In an example, a first logical channel may be assigned at least a firstlogical channel priority. In an example, the first logical channel maybe assigned one or more logical channel priorities for one or moreTTIs/transmission durations/numerologies. In an example, the firstlogical channel may be assigned a logical channel priority for each ofthe plurality of TTIs/transmission durations/numerologies. In anexample, a logical channel may be assigned a logical channel priorityfor each of one or more of the plurality of TTIs/transmissiondurations/numerologies. In an example, a logical channel may be assigneda logical channel priority for each of one or more TTIs/transmissiondurations/numerologies wherein the logical channel is mapped to the eachof the one or more TTIs/transmission durations/numerologies. In anexample, the one or more messages may comprise one or more second fieldsindicating priorities of a logical channel on one or moreTTIs/transmission durations/numerologies. In an example, the one or moresecond fields may comprise one or more sequences indicating prioritiesof a logical channel on one or more TTIs/transmissiondurations/numerologies. In an example, the one or more second fields maycomprise a plurality of sequences for the plurality of logical channels.A sequence corresponding to a logical channel may indicate thepriorities of the logical channel on the plurality of TTIs/transmissiondurations/numerologies/cells or one or more of the plurality ofTTIs/transmission durations/numerologies/cells. In an example, thepriorities may indicate mapping between a logical channel and one ormore TTIs/transmission duration/numerologies. In an example, a priorityof a logical channel with a given value (e.g., zero or minus infinity ora negative value) for a TTI/transmission duration/numerology mayindicate that the logical channel is not mapped to the TTI/transmissionduration/numerology. FIG. 15 illustrates an example with threeTTIs/transmission durations/numerologies and three logical channels(LC1, LC2, LC3) wherein LC1 is mapped to TTI/transmission duration1,TTI/transmission duration2, and TTI/transmission duration3 and LC2 ismapped to TTI/transmission duration2 and TTI/transmission duration3 andLC3 is mapped to TTI/transmission duration3. In an example, prioritiesof LC1 on TTI/transmission duration1, TTI/transmission duration2, andTTI/transmission duration3 may be indicated as (1, 2, 3), priorities ofLC2 on TTI/transmission duration1, TTI/transmission duration2, andTTI/transmission duration3 may be indicated as (0, 1, 2), priorities ofLC3 on TTI/transmission duration1, TTI/transmission duration2, andTTI/transmission duration3 may be indicated as (0, 0, 1). In an example,sizes of the sequence may be variable. In an example, a size of asequence associated with a logical channel may be a number ofTTIs/transmission durations/numerologies to which the logical channel ismapped. In an example, the sizes of the sequence may be fixed, e.g., thenumber of TTIs/transmission durations/numerologies/cells.

In an example, a TTI/transmission durations/numerology for a grant(e.g., as indicated by the grant/DCI) may not accept data from one ormore logical channels. In an example, the one or more logical channelsmay not be mapped to the TTI/transmission duration/numerology indicatedin the grant. In an example, a logical channel of the one or morelogical channels may be configured to be mapped to one or moreTTIs/transmission durations/numerologies and the TTI/numerology for thegrant may not be among the one or more TTIs/transmissiondurations/numerologies. In an example, a logical channel of the one ormore logical channels may be configured with a max-TTI/transmissionduration parameter indicating that the logical channel may not be mappedto a TTI/transmission duration longer than max-TTI/transmissionduration, and the grant may be for a TTI/transmission duration longerthan max-TTI/transmission duration. In an example, a logical channel maybe configured with a min-TTI/transmission duration parameter indicatingthat the logical channel may not be mapped to a TTI/transmissionduration shorter than min-TTI/transmission duration, and the grant maybe for a TTI/transmission duration shorter than min-TTI/transmissionduration. In an example, a logical channel may not be allowed to betransmitted on a cell and/or one or more numerologies and/or one or morenumerologies of a cell. In an example, a logical channel may containduplicate data and the logical channel may be restricted so that thelogical channel is not mapped to a cell/numerology. In an example, thelogical channel may not be configured with an upper layer configurationparameter laa-allowed and the cell may be an LAA cell.

In an example, a MAC entity and/or a multiplexing and assembly entity ofa MAC entity may perform a logical channel prioritization (LCP)procedure to allocate resources of one or more grants, indicated to awireless device by a base station using one or more DCIs, to one or morelogical channel. In an example, the timing between a grant/DCI receptiontime at the wireless device and transmission time may be dynamicallyindicated to the wireless device (e.g., at least using a parameter inthe grant/DCI). In an example, timing between a grant/DCI reception timeat the wireless device and transmission time may be fixed/preconfiguredand/or semi-statically configured. In an example, the LCP procedure forNR may consider the mapping of a logical channel to one or morenumerologies/TTIs, priorities of a logical channel on the one or morenumerologies/TTIs/transmission durations, thenumerology/TTI/transmission duration indicated in a grant, etc. The LCPprocedure may multiplex data from one or more logical channels to form aMAC PDU. The amount of data from a logical channel included in a MAC PDUmay depend on the QoS parameters of a bearer and/or service associatedwith the logical channel, priority of the logical channel on thenumerology/TTI/transmission duration indicated in the grant, etc. In anexample, one or more grants may be processed jointly at a wirelessdevice (e.g., resources of the one or more grants are allocatedsubstantially at a same time). In an example, one or more first grantsof the one or more grants may be grouped into a grouped grant withcapacity equal to sum of the capacities of the one or more first grantsand the resources of the grouped grant may be allocated to one or morelogical channels.

Example embodiments enhance triggering conditions for a wireless deviceto enable/disable packet duplication function.

Example A

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the PDCP layer (e.g., frequent undelivered PDCPPDUs). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage of PDCP PDUs thatwere not successfully transmitted/delivered. In an example, thepercentage may be measured for a time window. In an example, the timewindow may be pre-configured. In example, the value of time window maybe indicated by higher layers (e.g., RRC). In an example, the MAC entitymay duplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and a duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the RLC layer (e.g., frequent undelivered RLC PDUscorresponding to the bearer/PDCP entity configured with packetduplication). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage of RLC PDUs,corresponding to a bearer configured with duplication, that were notsuccessfully transmitted/delivered. In an example, the percentage may bemeasured for a time window. In an example, the time window may bepre-configured. In example, the value of time window may be indicated byhigher layers (e.g., RRC). In an example, the MAC entity may duplicatethe PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resourced indicatesin the DCI/grant and may transmit the TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria. In anexample, the one or more criteria may comprise frequent undelivered datapackets measured at the PHY/MAC layer (e.g., frequent HARQ NACKs and/orpoor channels conditions on one or more cells/numerologies mapped to alogical channel corresponding to a bearer configured with packetduplication). In an example, a threshold may be configured to triggerenabling/disabling the PDCP function for a bearer. In an example, thethreshold may be pre-configured. In an example, the threshold may beconfigured by higher layers (e.g., RRC). In an example, the thresholdmay be same for the bearers configured with packet duplication. In anexample, the threshold may be configured per bearer configured withpacket duplication. In an example, the threshold may be cell-specific.In an example, the threshold may indicate a percentage/number of HARQNACKs received for packets transmitted on one or more cells/numerologieswhere a logical channel corresponding to a bearer configured withduplication, is mapped to. In an example, the percentage may be measuredfor a time window. In an example, the time window may be pre-configured.In example, the value of time window may be indicated by higher layers(e.g., RRC). In an example, the threshold may indicate a thresholdchannel quality indicator (CQI). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and duplicate PDCP PDU may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. ADCI/grant may indicate the transmission parameters such as resources fortransmission, power control commands, HARQ parameters, modulation andcoding scheme (MCS), etc. The wireless device may perform a logicalchannel prioritization/multiplexing procedure and may allocate theresources of the grant/DC to one or more logical channels to create aMAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

Example embodiment enhance efficiency of logical channel multiplexing bydiscarding data that has already been transmitted from logical channelscorresponding to a bearer that is configured with packet duplication.

Example B

The NR radio access technology employs packet duplication at the PDCPlayer to enhance reliability for some service types (e.g., URLLC). Thepackets associated with a radio bearer are duplicated at PDCP layer. Thepackets of radio bearer and its duplicates are stored at buffersassociated with two logical channels corresponding to the radio bearer.Data from the two logical channels associated with the radio bearers aretransmitted via different cells and depending on the grants received onthe different cells, rate of depletion of data from the two logicalchannels may be different. Existing procedures for multiplexing data inuplink grants may lead to transmitting data that has been alreadytransmitted and acknowledged for multiple times and leads to inefficientradio link and degraded network throughput. The embodiments enhancelegacy data multiplexing procedures when a radio bearer is configuredwith packet duplication for a wireless device and the packet duplicationis activated for the wireless device.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signaling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signaling (e.g., PDCCH like signaling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled (not configured). In an example, aPDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, if a first logical channelwith PDCP PDUs (or duplicate PDCP PDUs) of a bearer configured withpacket duplication contains a first amount of data (e.g., X bytes or XPDCP PDUs/RLC SDUs) and a second logical channel with duplicate PDCPPDUs (or PDCP PDUs) of a bearer configured with packet duplicationcontains a second amount of data (e.g., Y bytes or Y PDCP PDUs/RLCSDUs), and the first amount of data is larger than the second amount ofdata, the wireless device MAC entity may discard a portion of data inthe first logical channel that has been transmitted and acknowledged(e.g., HARQ ACKed and/or RLC ACKed). In an example, if the first amountof data is X bytes and the second amount of data is Y bytes and X islarger than Y, the wireless device may discard as much as (X-Y-unACKeddata) on top of the buffer for the first logical channel. In an examplewith more than one logical channel containing duplicate PDCP PDUs, thewireless device MAC entity may discard a portion of data that has beentransmitted and acknowledged (e.g., HARQ ACKed and/or RLC ACKed) in atleast one logical channel from a plurality of logical channelscorresponding to the same bearer. In an example, if the buffer for alogical channel that contains PDCP PDUs or duplicate PDCP PDUs for abearer configured with packet duplication is emptied and the last datain the buffer is acknowledged (e.g., HARQ ACKed and/or RLC ACKed) aftertransmission, the wireless device MAC entity may empty one or morelogical channels corresponding to the radio bearer (e.g., logicalchannels containing PDCP PDUs or duplicate PDCP PDUs from the bearer).In an example, the wireless device may perform the data discardingprocess described in configured times.

In an example, the wireless device may perform duplicate data discardwhen a buffer status report is triggered and/or when the wireless devicecreates the buffer status report MAC CE. In an example, the wirelessdevice may receive one or more DCIs/grants for transmission on one ormore cells e.g., for one or more numerologies/TTIs on the one or morecells. A DCI/grant may indicate the transmission parameters such asresources for transmission, power control commands, HARQ parameters,modulation and coding scheme (MCS), etc. The wireless device may performa logical channel prioritization/multiplexing procedure and may allocatethe resources of the grant/DC to one or more logical channels to createa MAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

In an example embodiment, as shown in FIG. 16, a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise configuration parameters for one ormore bearers comprising a first radio bearer. In an example, the firstradio bearer is a data radio bearer. In an example, the first radiobearer may correspond to an ultra-reliable low-latency communications(URLLC) service type. In an example, the first radio bearer is asignaling radio bearer. The configuration parameters may comprise afirst information element indicating that packet duplication isconfigured for the first radio bearer. The wireless device may receive aMAC control element indicating activation of packet duplication for thefirst radio bearer. In an example, the first radio bearer may correspondto a first logical channel and a second logical channel. In an example,packets (e.g., PDCP packets) associated with the first radio bearer areduplicated in the first logical channel and the second logical channel.In an example, a first packet corresponding to the first logical channelmay correspond to a first radio link control entity. In an example, asecond packet corresponding to the second logical channel may correspondto a second radio link control entity. In an example, the one or moremessages may comprise logical channel configuration parametersindicating that one or more first cells are first allowed serving cellsfor the first logical channel; and one or more second cells are secondallowed serving cells for the second logical channel. The one or moresecond cells may be different from the one or more first cells.

The wireless device may receive an uplink grant for transmission of oneor more transport blocks. The uplink grant may comprise transmissionparameters for the one or more first transport blocks. The transmissionparameters may comprise radio resource allocation parameters, powercontrol related parameters, HARQ related parameters, etc. The wirelessdevice may transmit the one or more first transport blocks. The one ormore first transport blocks may comprise data of one or more firstbuffers associated with the first logical channel. The uplink grant maybe for a first cell in the one or more first cells associated with thefirst logical channel. The wireless device may receive anacknowledgement for the one or more first transport blocks in responseto transmitting the one or more first transport blocks. In an example,the acknowledgement may be a HARQ/MAC layer acknowledgement. In anexample, the acknowledgement may be a radio link control layeracknowledgment. In an example, the acknowledgment may be a PDCP layeracknowledgment. The wireless device and/or base station may perform aduplicate discard function at the PDCP layer.

As shown in FIG. 16, in response to transmission of the one or morefirst transport blocks, one or more buffers associated with the firstlogical channel may be emptied. The wireless device may flush one ormore second buffers associated with the second logical channel inresponse to the one or more first buffers being emptied in response tothe transmission of the one or more first TBs. The flushing the one ormore second buffers associated with the second logical channel maycomprise ignoring/discarding data in the one or more second buffersassociated with the second logical channel. In an example, the wirelessdevice may receive a second uplink grant for transmission of one or moresecond transport blocks. The second uplink grant may comprise secondtransmission parameters for transmission of the one or more secondtransport blocks. The wireless device may transmit the one or moresecond transport blocks employing the second transmission parameters.

Example embodiments enhance buffer status reporting when one or morebearers are configured with packet duplication.

Example C

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, the MAC entity may duplicate the PDCP PDUs for a bearerfor which the duplication is configured/enabled and may not duplicatePDCP PDUs for a bearer for which the duplication is disabled (notconfigured). In an example, a PDCP PDU and duplicate PDCP PDUs maycorrespond to different RLC entities/logical channels. In an example, awireless device MAC entity may perform data discard process (e.g., asdescribed in Example B embodiments). In an example, a wireless deviceMAC entity may perform data discard process (e.g., as described inExample B embodiments) when a buffer status report is triggered and/orwhen a buffer status report MAC CE is created. One or more logicalchannels corresponding to a bearer configured with packet duplicationfor which packet duplication is enabled (e.g., enabled by the basestation) may have substantially same amount of data (e.g., when thebuffer status report MAC CE is created). In an example, a logicalchannel of the one or more logical channels may have as much asunacknowledged data less data in the logical channel's buffer comparedto other logical channels in the one or more logical channels. In anexample, if the base station configures/enables the packet duplicationfor a bearer configured for the wireless device, a plurality of logicalchannels may correspond to bearer. In an example, the buffer statusreport may comprise buffer status of one logical channels correspondingto the bearer (e.g., logical channels comprising PDCP PDUs). In anexample, the wireless device may receive one or more DCIs/grants fortransmission on one or more cells e.g., for one or morenumerologies/TTIs on the one or more cell. A DCI/grant may indicate thetransmission parameters such as resources for transmission, powercontrol commands, HARQ parameters, modulation and coding scheme (MCS),etc. The wireless device may perform a logical channelprioritization/multiplexing procedure and may allocate the resources ofthe grant/DC to one or more logical channels to create a MAC PDU. In anexample, the one or more logical channels may comprise logical channelswith data and/or duplicate data. In an example, the MAC layer maydeliver the MAC PDU to Physical layer to create a transport block (TB).The wireless device may calculate transmission power for the TB using atleast the power control commands in the grant/DCI. The Physical layermay map the TB to the time/frequency resources indicated in theDCI/grant and may transmit the TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, a UEmay autonomously enable/disable the PDCP packet duplication for a bearerconsidering one or more criteria (e.g., as described in Example Aembodiments). In an example, the MAC entity may duplicate the PDCP PDUsfor a bearer for which the duplication is configured/enabled and may notduplicate PDCP PDUs for a bearer for which the duplication is disabledand/or not configured. In an example, a PDCP PDU and duplicate PDCP PDUsmay correspond to different RLC entities/logical channels. In anexample, a wireless device MAC entity may perform data discard process(e.g., as described in Example B embodiments). In an example, a wirelessdevice MAC entity may perform data discard process (e.g., as describedin Example B embodiments) when a buffer status report is triggeredand/or when a buffer status report MAC CE is created. One or morelogical channels corresponding to a bearer configured with packetduplication for which packet duplication is enabled (e.g., enabledautonomously by the wireless device) may have substantially same amountof data (e.g., when the buffer status report MAC CE is created). In anexample, a logical channel of the one or more logical channels may haveas much as unacknowledged data less data in the logical channel's buffercompared to other logical channels in the one or more logical channels.In an example, if the wireless device autonomously enables the packetduplication for a bearer configured for the wireless device (and/orconfigured with packet duplication), a plurality of logical channels maycorrespond to bearer. In an example, the buffer status report maycomprise buffer status of one logical channels corresponding to thebearer (e.g., logical channels comprising PDCP PDUs). In an example, thebuffer status report may comprise an indication that a logical channelhas a corresponding logical channel with duplicate data. In an example,the indication may be in form of a bit map. In an example, theindication may be in the MAC subheader corresponding to the BSR. In anexample, a value of one in the bit map corresponding to a logicalchannel may indicate that there is one or more logical channelscorresponding to the logical channel with duplicate data. In an example,the wireless device may receive one or more DCIs/grants for transmissionon one or more cells e.g., for one or more numerologies/TTIs on the oneor more cell. A DCI/grant may indicate the transmission parameters suchas resources for transmission, power control commands, HARQ parameters,modulation and coding scheme (MCS), etc. The wireless device may performa logical channel prioritization/multiplexing procedure and may allocatethe resources of the grant/DC to one or more logical channels to createa MAC PDU. In an example, the one or more logical channels may compriselogical channels with data and/or duplicate data. In an example, the MAClayer may deliver the MAC PDU to Physical layer to create a transportblock (TB). The wireless device may calculate transmission power for theTB using at least the power control commands in the grant/DCI. ThePhysical layer may map the TB to the time/frequency resources indicatedin the DCI/grant and may transmit the TB.

Example embodiment enhance the HARQ retransmission procedure when one ormore bearers are configured with packet duplication.

Example D

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more cells. In an example, the base station mayconfigure a logical channel not be transmitted on an LAA cell. In anexample, the base station may configure a logical channel with a bitmapindicating the one or more cells that a logical channel may and/or maynot be mapped to (e.g., data from the logical channel may and/or may notbe transmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI. The DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. In an example, thewireless device may multiplex data from a logical channel that isconfigured to not be transmitted on one or more cells and create a firstMAC PDU. In an example, the one or more cells may not comprise the firstcell. The physical layer may create a first TB using the first MAC PDU.The wireless device may calculate power for the first TB using at leastthe power control commands in the DCI/grant and may map the TB to theresources indicated in the DCI/grant and may transmit the TB. In anexample, a HARQ entity may handle transmission and/or retransmission oftransport blocks on a plurality of cells comprising the first cell. Inan example, the wireless device may receive a NACK and/or a secondDCI/grant indicating retransmission of the first TB (or a new redundancyversion of the first TB). In an example, the DCI/grant may indicate theHARQ retransmission of the first TB on a second cell of the plurality ofcells. In an example, the second cell may not be among the one or morecells. The wireless device may transmit the HARQ retransmission of thefirst TB e.g., using the transmission parameters (e.g., resources)indicated in the second DCI/grant. In an example, the HARQ entity may beindicated that there is a restriction for a TB (e.g., corresponding to aHARQ process) not to be transmitted on the one one or more cells.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more cells. In an example, the base station mayconfigure a logical channel not be transmitted on an LAA cell. In anexample, the base station may configure a logical channel with a bitmapindicating the one or more cells that a logical channel may and/or maynot be mapped to (e.g., data from the logical channel may and/or may notbe transmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI. The DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. In an example, thewireless device may multiplex data from a logical channel that isconfigured to not be transmitted on one or more cells and create a firstMAC PDU. In an example, the one or more cells may not comprise the firstcell. The physical layer may create a first TB using the first MAC PDU.The wireless device may calculate power for the first TB using at leastthe power control commands in the DCI/grant and may map the TB to theresources indicated in the DCI/grant and may transmit the TB. In anexample, a HARQ entity may handle transmission and/or retransmission oftransport blocks on a plurality of cells comprising the first cell. Inan example, the wireless device may receive a NACK and/or a secondDCI/grant indicating retransmission of the first TB (or a new redundancyversion of the first TB). In an example, the DCI/grant may indicate theHARQ retransmission of the first TB on a second cell of the plurality ofcells. In an example, the second cell may be among the one or morecells. The wireless device may transmit the HARQ retransmission of thefirst TB e.g., using the transmission parameters (e.g., resources)indicated in the second DCI/grant.

Example E

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more numerologies/TTIs. In an example, the basestation may configure a logical channel with a bitmap indicating the oneor more numerologies/TTIs that a logical channel may and/or may not bemapped to (e.g., data from the logical channel may and/or may not betransmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI. The DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. In an example, thewireless device may multiplex data from a logical channel that isconfigured to not be transmitted on one or more numerologies/TTIs andcreate a first MAC PDU. In an example, the one or more numerologies/TTIsmay not comprise the first numerology/TTI. The physical layer may createa first TB using the first MAC PDU. The wireless device may calculatepower for the first TB using at least the power control commands in theDCI/grant and may map the TB to the resources indicated in the DCI/grantand may transmit the TB. In an example, HARQ entity may handletransmission and/or retransmission of transport blocks on a plurality ofTTIs/numerologies of the first cell comprising the first TTI/numerology.In an example, the wireless device may receive a NACK and/or a secondDCI/grant indicating retransmission of the first TB (or a new redundancyversion of the first TB). In an example, the DCI/grant may indicate theHARQ retransmission of the first TB on a second TTI/numerology of theplurality of TTIs/numerologies. In an example, the second TTI/numerologymay not be among the one or more TTIs/numerologies. The wireless devicemay transmit the HARQ retransmission of the first TB e.g., using thetransmission parameters (e.g., resources) indicated in the secondDCI/grant. In an example, the HARQ entity may be indicated that there isa restriction for a TB (e.g., corresponding to a HARQ process) not to betransmitted on the one one or more TTIs/numerologies.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the base station may configurea logical channel (e.g., containing duplicate data) not to betransmitted on one or more numerologies/TTIs. In an example, the basestation may configure a logical channel with a bitmap indicating the oneor more numerologies/TTIs that a logical channel may and/or may not bemapped to (e.g., data from the logical channel may and/or may not betransmitted on). In an example, the wireless device may receive aDCI/grant for transmission on a first cell e.g., for a firstnumerology/TTI. The DCI/grant may indicate the transmission parameterssuch as resources for transmission, power control commands, HARQparameters, modulation and coding scheme (MCS), etc. In an example, thewireless device may multiplex data from a logical channel that isconfigured to not be transmitted on one or more numerologies/TTIs andcreate a first MAC PDU. In an example, the one or more numerologies/TTIsmay not comprise the first numerology/TTI. The physical layer may createa first TB using the first MAC PDU. The wireless device may calculatepower for the first TB using at least the power control commands in theDCI/grant and may map the TB to the resources indicated in the DCI/grantand may transmit the TB. In an example, HARQ entity may handletransmission and/or retransmission of transport blocks on a plurality ofTTIs/numerologies of the first cell comprising the first TTI/numerology.In an example, the wireless device may receive a NACK and/or a secondDCI/grant indicating retransmission of the first TB (or a new redundancyversion of the first TB). In an example, the DCI/grant may indicate theHARQ retransmission of the first TB on a second TTI/numerology of theplurality of TTIs/numerologies. In an example, the second TTI/numerologymay be among the one or more TTIs/numerologies. The wireless device maytransmit the HARQ retransmission of the first TB e.g., using thetransmission parameters (e.g., resources) indicated in the secondDCI/grant.

Example F

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, a wireless device MAC entitymay perform data discard process (e.g., as described in Example Bembodiments). The buffers for logical channels corresponding to data andduplicate data may have same data. In an example, the wireless devicemay receive a plurality of DCIs/grants. A grant/DCI in the plurality ofDCIs/grants may comprise transmission parameters (e.g., time/frequencyresources, HARQ parameters, MCS, power control commands, etc.). In anexample, the wireless device may create a plurality of TBs using to theplurality of DCIs/grants. In an example, each of the plurality of TBsmay contain data from a logical channel of the plurality of logicalchannels corresponding to a same bearer (e.g., bearer configured withpacket duplication). In an example, a first TB of the plurality of TBsmay comprise only data from a logical channel corresponding to thebearer. The wireless device may receive an ACK for other TBs in theplurality of TBs. The wireless device may stop transmission orretransmission of the first TB. The wireless device may flush the HARQbuffer corresponding to the first TB.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, a wireless device MAC entitymay perform data discard process (e.g., as described in Example Bembodiments). The buffers for logical channels corresponding to data andduplicate data may have same data. In an example, the wireless devicemay receive a plurality of DCIs/grants for a same TTI on a plurality ofcells. A grant/DCI in the plurality of DCIs/grants may comprisetransmission parameters (e.g., time/frequency resources, HARQparameters, MCS, power control commands, etc.). In an example, thewireless device may create a plurality of TBs using to the plurality ofDCIs/grants. In an example, each of the plurality of TBs may containdata from a logical channel of the plurality of logical channelscorresponding to a same bearer (e.g., bearer configured with packetduplication). In an example, a first TB of the plurality of TBs maycomprise only data from a logical channel corresponding to the bearer.The wireless device calculate power for the plurality of TBs at leastusing the power control commands indicated in the plurality ofDCIs/grants. In an example, the wireless device may drop the first TB ifthe wireless is power limited e.g., if the total calculated power islarger than the UE maximum transmit power.

Example embodiments enhance the efficiency of BSR and PHR reporting whena plurality of MAC entities handle transmission of data from logicalchannels that contain data and duplicate data.

Example G

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. In anexample, the cells may belong to different cells groups corresponding todifferent MAC entities. A DCI/grant may indicate the transmissionparameters such as resources for transmission, power control commands,HARQ parameters, modulation and coding scheme (MCS), etc. The wirelessdevice may perform a logical channel prioritization/multiplexingprocedure and may allocate the resources of the grant/DC to one or morelogical channels to create a MAC PDU. In an example, the one or morelogical channels may comprise logical channels with data and/orduplicate data. In an example, the MAC layer may deliver the MAC PDU toPhysical layer to create a transport block (TB). The wireless device maycalculate transmission power for the TB using at least the power controlcommands in the grant/DCI. The Physical layer may map the TB to thetime/frequency resources indicated in the DCI/grant and may transmit theTB. In an example a plurality of MAC entities may be configured for theplurality of logical channels corresponding to data and duplicate PDCPPDUs for a bearer configured with packet duplication. In an example, thebase station may configure a plurality of cells for the wireless device.In an example, the base station may configure a cell of the plurality ofcells to one of a plurality of cells groups. In an example, a cell groupmay be configured that handle transmission and retransmission of logicalchannels comprising PDCP PDUs. In an example, a cell group may beconfigured that handle transmission and retransmission of duplicate PDCPPDUs. In an example, the wireless device may transmit a plurality ofBSRs corresponding to the plurality of MAC entities to the base station,each BSR comprising buffer status for logical channels corresponding tological channels handled by a MAC entity.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. In anexample, the cells may belong to different cells groups corresponding todifferent MAC entities. A DCI/grant may indicate the transmissionparameters such as resources for transmission, power control commands,HARQ parameters, modulation and coding scheme (MCS), etc. The wirelessdevice may perform a logical channel prioritization/multiplexingprocedure and may allocate the resources of the grant/DC to one or morelogical channels to create a MAC PDU. In an example, the one or morelogical channels may comprise logical channels with data and/orduplicate data. In an example, the MAC layer may deliver the MAC PDU toPhysical layer to create a transport block (TB). The wireless device maycalculate transmission power for the TB using at least the power controlcommands in the grant/DCI. The Physical layer may map the TB to thetime/frequency resources indicated in the DCI/grant and may transmit theTB. In an example a plurality of MAC entities may be configured for theplurality of logical channels corresponding to data and duplicate PDCPPDUs for a bearer configured with packet duplication. In an example, thebase station may configure a plurality of cells for the wireless device.In an example, the base station may configure a cell of the plurality ofcells to one of a plurality of cells groups. In an example, a cell groupmay be configured that handle transmission and retransmission of logicalchannels comprising PDCP PDUs. In an example, a cell group may beconfigured that handle transmission and retransmission of duplicate PDCPPDUs. In an example, the wireless device may transmit a BSR to the basestation, the BSR comprising buffer status for logical channels handledby the plurality of MAC entity. The BSR may be used by the plurality ofMAC entities for scheduling the wireless device.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. In anexample, the cells may belong to different cells groups corresponding todifferent MAC entities. A DCI/grant may indicate the transmissionparameters such as resources for transmission, power control commands,HARQ parameters, modulation and coding scheme (MCS), etc. The wirelessdevice may perform a logical channel prioritization/multiplexingprocedure and may allocate the resources of the grant/DC to one or morelogical channels to create a MAC PDU. In an example, the one or morelogical channels may comprise logical channels with data and/orduplicate data. In an example, the MAC layer may deliver the MAC PDU toPhysical layer to create a transport block (TB). The wireless device maycalculate transmission power for the TB using at least the power controlcommands in the grant/DCI. The Physical layer may map the TB to thetime/frequency resources indicated in the DCI/grant and may transmit theTB. In an example a plurality of MAC entities may be configured for theplurality of logical channels corresponding to data and duplicate PDCPPDUs for a bearer configured with packet duplication. In an example, thebase station may configure a plurality of cells for the wireless device.In an example, the base station may configure a cell of the plurality ofcells to one of a plurality of cells groups. In an example, a cell groupmay be configured that handle transmission and retransmission of logicalchannels comprising PDCP PDUs. In an example, a cell group may beconfigured that handle transmission and retransmission of duplicate PDCPPDUs. In an example, the wireless device may transmit a power headroomreport (PHR) corresponding to a grant/DCI received from a MAC entity tothe base station.

In an example embodiment, a wireless device may receive one or moremessages from a base station (e.g., NR gNB or eLTE eNB). In an example,the one or more messages may comprise configuration parameters for aplurality of logical channels. In an example, the plurality of logicalchannels may comprise logical channels with data and/or logical channelswith duplicate data. In an example, the one or more messages maycomprise configuration parameters for a plurality of data radio bearers(DRBs) and/or signalling radio bearers (SRBs). In an example, theconfiguration parameters for DRBs/SRBs may configure PDCP packetduplication with carrier aggregation for a DRB/SRB. In an example, thebase station may enable/disable packet duplication using physical layerand/or MAC layer signalling (e.g., PDCCH like signalling, MAC CE, etc.).In an example, a UE may autonomously enable/disable the PDCP packetduplication for a bearer considering one or more criteria (e.g., asdescribed in Example A embodiments). In an example, the MAC entity mayduplicate the PDCP PDUs for a bearer for which the duplication isconfigured/enabled and may not duplicate PDCP PDUs for a bearer forwhich the duplication is disabled and/or not configured. In an example,a PDCP PDU and duplicate PDCP PDUs may correspond to different RLCentities/logical channels. In an example, the wireless device mayreceive one or more DCIs/grants for transmission on one or more cellse.g., for one or more numerologies/TTIs on the one or more cells. In anexample, the cells may belong to different cells groups corresponding todifferent MAC entities. A DCI/grant may indicate the transmissionparameters such as resources for transmission, power control commands,HARQ parameters, modulation and coding scheme (MCS), etc. The wirelessdevice may perform a logical channel prioritization/multiplexingprocedure and may allocate the resources of the grant/DC to one or morelogical channels to create a MAC PDU. In an example, the one or morelogical channels may comprise logical channels with data and/orduplicate data. In an example, the MAC layer may deliver the MAC PDU toPhysical layer to create a transport block (TB). The wireless device maycalculate transmission power for the TB using at least the power controlcommands in the grant/DCI. The Physical layer may map the TB to thetime/frequency resources indicated in the DCI/grant and may transmit theTB. In an example a plurality of MAC entities may be configured for theplurality of logical channels corresponding to data and duplicate PDCPPDUs for a bearer configured with packet duplication. In an example, thebase station may configure a plurality of cells for the wireless device.In an example, the base station may configure a cell of the plurality ofcells to one of a plurality of cells groups. In an example, a cell groupmay be configured that handle transmission and retransmission of logicalchannels comprising PDCP PDUs. In an example, a cell group may beconfigured that handle transmission and retransmission of duplicate PDCPPDUs. In an example, the wireless device may transmit a power headroomreport (PHR) corresponding to a grant/DCI received from any MAC entityto the base station.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 17 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1710, a wireless device may receive one ormore messages comprising configuration parameters for a first radiobearer; and a first information element indicating that packetduplication is configured for the first radio bearer. At 1720, a controlelement indicating activation of the packet duplication for the firstradio bearer corresponding to a first logical channel and a secondlogical channel may be received. At 1730, a first uplink grant fortransmission of one or more first transport blocks (TBs) may bereceived. At 1740, the one or more first TBs may be transmitted. The oneor more first TBs may comprise data of one or more first buffersassociated with the first logical channels. At 1750, acknowledgement forthe one or more first TBs may be received. At 1760, one or more secondbuffers associated with the second logical channel may be flushed inresponse to the one or more first buffers being emptied in response tothe transmission of the one or more first TBs.

According to an embodiment, packets associated with the first radiobearer may be duplicated in the first logical channel and the secondlogical channel. According to an embodiment, the first radio bearer maybe one of a data radio bearer or a signaling radio bearer. According toan embodiment, the one or more messages may comprise logical channelconfiguration parameters indicating that: one or more first cells arefirst allowed serving cells for the first logical channel; and one ormore second cells are second allowed serving cells for the secondlogical channel. The one or more second cells may be different from theone or more first cells. According to an embodiment, the one or morefirst cells may comprise a first cell; and the first uplink grant is forthe first cell. According to an embodiment, the logical channelconfiguration parameters may further indicate that: the first logicalchannel is mapped to one or more first transmission durations; and thesecond logical channel is mapped to one or more second transmissiondurations. According to an embodiment, the acknowledgement may be atleast one of the medium access control layer acknowledgement or radiolink control layer acknowledgement or packet data convergence protocollayer acknowledgement. According to an embodiment, a duplicate discardfunction may be performed at a packet data convergence protocol layer.According to an embodiment, a first packet may correspond to the firstlogical channel corresponds to a first radio link control entity; and asecond packet may correspond to the second logical channel correspondsto a second radio link control entity. According to an embodiment, thefirst radio bearer may correspond to an ultra-reliable low-latencycommunications service type.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, an indication for activation of packet data convergence protocol(PDCP) packet duplication of a radio bearer associated with a firstradio link control (RLC) entity and a second RLC entity; duplicating apacket of the radio bearer; providing: the packet to the first RLCentity; and a duplicate packet to the second RLC entity; transmittingthe packet of the first RLC entity; receiving an acknowledgement of asuccessful delivery for the packet of the first RLC entity; and inresponse to the acknowledgement, discarding the duplicate packet of thesecond RLC entity.
 2. The method of claim 1, wherein: the providing thepacket to the first RLC entity comprises providing the packet to a firstlogical channel associated with the first RLC entity; and the providingthe duplicate packet to the second RLC entity comprises providing theduplicate packet to a second logical channel associated with the secondRLC entity.
 3. The method of claim 1, wherein the packet is a PDCP dataprotocol data unit.
 4. The method of claim 1, further comprising:receiving, by a wireless device, one or more radio resource control(RRC) messages comprising: configuration parameters for the radiobearer; and a first information element indicating that the PDCP packetduplication is configured for transmission of packets of the radiobearer.
 5. The method of claim 4, wherein the one or more RRC messagescomprise logical channel configuration parameters indicating that: oneor more first cells are first allowed serving cells for a first logicalchannel associated with the first RLC entity; and one or more secondcells are second allowed serving cells for the second logical channelassociated with the second RLC entity.
 6. The method of claim 5, whereinthe logical channel configuration parameters further indicate that: thefirst logical channel is mapped to one or more first transmissiondurations; and the second logical channel is mapped to one or moresecond transmission durations.
 7. The method of claim 6, furthercomprising receiving an uplink grant for transmission of the packet. 8.The method of claim 1, wherein the acknowledgement is at least one of amedium access control layer acknowledgement or an RLC layeracknowledgement or a PDCP layer acknowledgement.
 9. The method of claim1, wherein the method comprises performing a duplicate discard functionat a PDCP layer.
 10. The method of claim 1, wherein: the packet mappedto the first logical channel corresponds to a first buffer; and theduplicate data packet mapped to the second logical channel correspondsto a second buffer.
 11. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive anindication for activation of packet data convergence protocol (PDCP)packet duplication of a radio bearer associated with a first radio linkcontrol (RLC) entity and a second RLC entity; duplicate a packet of theradio bearer; providing: the packet to the first RLC entity; and aduplicate packet to the second RLC entity; transmit the packet of thefirst RLC entity; receiving an acknowledgement of a successful deliveryfor the packet of the first RLC entity; and in response to theacknowledgement, discard the duplicate packet of the second RLC entity.12. The wireless device of claim 11, wherein: the providing the packetto the first RLC entity comprises providing the packet to a firstlogical channel associated with the first RLC entity; and the providingthe duplicate packet to the second RLC entity comprises providing theduplicate packet to a second logical channel associated with the secondRLC entity.
 13. The wireless device of claim 11, wherein the packet is aPDCP data protocol data unit.
 14. The wireless device of claim 11,wherein the instructions, when executed by the one or more processors,further cause the wireless device to receive one or more radio resourcecontrol (RRC) messages comprising: configuration parameters for theradio bearer; and a first information element indicating that the PDCPpacket duplication is configured for transmission of packets of theradio bearer.
 15. The wireless device of claim 14, wherein the one ormore RRC messages comprise logical channel configuration parametersindicating that: one or more first cells are first allowed serving cellsfor a first logical channel associated with the first RLC entity; andone or more second cells are second allowed serving cells for the secondlogical channel associated with the second RLC entity.
 16. The wirelessdevice of claim 15, wherein the logical channel configuration parametersfurther indicate that: the first logical channel is mapped to one ormore first transmission durations; and the second logical channel ismapped to one or more second transmission durations.
 17. The wirelessdevice of claim 16, wherein the instructions, when executed by the oneor more processors, further cause the wireless device to receive anuplink grant for transmission of the packet.
 18. The wireless device ofclaim 11, wherein the acknowledgement is at least one of a medium accesscontrol layer acknowledgement or an RLC layer acknowledgement or a PDCPlayer acknowledgement.
 19. The wireless device of claim 11, wherein: thepacket mapped to the first logical channel corresponds to a firstbuffer; and the duplicate data packet mapped to the second logicalchannel corresponds to a second buffer.
 20. A system comprising: a basestation comprising: one or more first processors; and first memorystoring first instructions that, when executed by the one or more firstprocessors, cause the base station to: transmit an indication foractivation of packet data convergence protocol (PDCP) packet duplicationof a radio bearer associated with a first radio link control (RLC)entity and a second RLC entity; a wireless device comprising: one ormore second processors; and second memory storing second instructionsthat, when executed by the one or more second processors, cause thewireless device to: receive the indication; duplicate a packet of theradio bearer; providing: the packet to the first RLC entity; and aduplicate packet to the second RLC entity; transmit the packet of thefirst RLC entity; receiving an acknowledgement of a successful deliveryfor the packet of the first RLC entity; and in response to theacknowledgement, discard the duplicate packet of the second RLC entity.